Cisco Switching Black Book...............................................................................................................................1
In Depth...................................................................................................................................................6
Physical Media and Switching Types......................................................................................................6
A Bit of History.......................................................................................................................................7
The Cisco IOS........................................................................................................................................24
Connecting to the Switch................................................................................................................25
Powering Up the Switch..................................................................................................................25
The Challenges.......................................................................................................................................27
In Depth.................................................................................................................................................30
Configuring RMON on a Set/Clear−Based Interface.....................................................................51
Using Set/Clear Command Set Recall Key Sequences..........................................................................52
Using IOS−Based Command Editing Keys and Functions...................................................................52
Chapter 3: WAN Switching.............................................................................................................................54
In Depth.................................................................................................................................................54
WAN Transmission Media....................................................................................................................55
Synchronous Transport Signal (STS)..............................................................................................56
Cisco WAN Switches............................................................................................................................57
Assigning a Switch Hostname.........................................................................................................65
Displaying a Summary of All Modules...........................................................................................66
Displaying Detailed Information for the Current Card...................................................................66
Changing the Time and Date...........................................................................................................66
Displaying the Configuration of the Maintenance and Control Ports.............................................66
Displaying the IP Address...............................................................................................................66
Configuring the IP Interface............................................................................................................67
Displaying the Alarm Level of the Switch......................................................................................67
Table of Contents
Chapter 4: LAN Switch Architectures............................................................................................................68
In Depth.................................................................................................................................................68
The Catalyst Crescendo Architecture....................................................................................................68
Viewing the Adjacency Table on the 8500 GSR...................................................................................83
Clearing the Adjacency Table on the 8500 GSR...................................................................................83
Enabling Console Session Logging on a Set/Clear Command−Based IOS..........................................83
Enabling Telnet Session Logging on a Set/Clear Command−Based IOS.............................................84
Disabling Console Session Logging on a Set/Clear Command−Based IOS.........................................84
Disabling Telnet Session Logging on a Set/Clear Command−Based IOS............................................84
Setting the System Message Severity Levels on a Set/Clear Command−Based IOS............................84
Enabling the Logging Time Stamp on a Set/Clear Command−Based Switch......................................84
Disabling the Logging Time Stamp on a Set/Clear Command−Based Switch.....................................85
Configuring the Logging Buffer Size on a Set/Clear Command−Based Switch...................................85
Clearing the Server Logging Table........................................................................................................85
Disabling Server Logging......................................................................................................................85
Displaying the Logging Configuration..................................................................................................86
Displaying System Logging Messages..................................................................................................86
iv
Table of Contents
Chapter 5: Virtual Local Area Networks.......................................................................................................88
In Depth.................................................................................................................................................88
The Flat Network of Yesterday..............................................................................................................88
Why Use VLANs?.................................................................................................................................89
Configuring VTP Pruning on a Set/Clear CLI Switch........................................................................112
Disabling Pruning for Unwanted VLANs............................................................................................112
Configuring IP InterVLAN Routing on an External Cisco Router......................................................112
Configuring IPX InterVLAN Routing on an External Router.............................................................113
v
Table of Contents
Chapter 6: InterVLAN and Basic Module Configuration..........................................................................114
In Depth...............................................................................................................................................114
Port Security..................................................................................................................................123
Manually Configured MAC Addresses.........................................................................................123
Determining the Slot Number in Which a Module Resides................................................................123
Accessing the Internal Route Processor from the Switch....................................................................124
Configuring a Hostname on the RSM..................................................................................................124
Assigning an IP Address and Encapsulation Type to an Ethernet Interface........................................125
Setting the Port Speed and Port Name on an Ethernet Interface.........................................................125
Configuring a Default Gateway on a Catalyst 5000............................................................................126
Verifying the IP Configuration on a Catalyst 5000.............................................................................126
Enabling RIP on an RSM.....................................................................................................................126
Viewing the RSM’s Running Configuration.......................................................................................127
Configuring InterVLAN Routing on an RSM.....................................................................................127
Configuring IPX InterVLAN Routing on the RSM.............................................................................128
Configuring AppleTalk InterVLAN Routing on an RSM...................................................................128
Viewing the RSM Configuration.........................................................................................................129
Assigning a MAC Address to a VLAN...............................................................................................129
Viewing the MAC Addresses..............................................................................................................129
Configuring Filtering on an Ethernet Interface....................................................................................130
Configuring Port Security on an Ethernet Module..............................................................................130
Clearing MAC Addresses....................................................................................................................131
Configuring the Catalyst 5000 Supervisor Engine Module.................................................................131
Setting the boot config−register on the Supervisor Engine Module....................................................132
Changing the Management VLAN on a Supervisor Engine................................................................133
Viewing the Supervisor Engine Configuration....................................................................................133
Configuring the Cisco 2621 External Router for ISL Trunking..........................................................134
Configuring Redundancy Using HSRP...............................................................................................135
Chapter 7: IP Multicast..................................................................................................................................137
In Depth...............................................................................................................................................137
IP Multicasting Overview....................................................................................................................137
Chapter 8: WAN Cell Switching...................................................................................................................160
In Depth...............................................................................................................................................160
In Depth...............................................................................................................................................183
In Depth...............................................................................................................................................199
In Depth...............................................................................................................................................227
How MLS Works.................................................................................................................................227
Chapter 12: Hot Standby Routing Protocol.................................................................................................243
In Depth...............................................................................................................................................243
The Solution.........................................................................................................................................245
In Depth...............................................................................................................................................254
Enabling Port Security.........................................................................................................................269
Displaying the MAC Address Table....................................................................................................270
Chapter 14: Web Management......................................................................................................................272
In Depth...............................................................................................................................................272
Standard and Enterprise Edition CVSM..............................................................................................272
CVSM Default Home Page..................................................................................................................273
The Switch Image..........................................................................................................................274
Configuring the Switch with an IP Address and Setting the Default Web Administration Port.........275
Connecting to the Web Management Console.....................................................................................276
Configuring the Switch Port Analyzer.................................................................................................281
Chapter 15: The Standard Edition IOS........................................................................................................283
In Depth...............................................................................................................................................283
The 1900 and 2820 Series Switches....................................................................................................283
Main Menu Choices......................................................................................................................283
In Depth...............................................................................................................................................309
This book may not be duplicated in any way without the express written consent of the publisher, except in
the form of brief excerpts or quotations for the purposes of review. The information contained herein is for the
personal use of the reader and may not be incorporated in any commercial programs, other books, databases,
or any kind of software without written consent of the publisher. Making copies of this book or any portion
for any purpose other than your own is a violation of United States copyright laws.
Limits of Liability and Disclaimer of Warranty
The author and publisher of this book have used their best efforts in preparing the book and the programs
contained in it. These efforts include the development, research, and testing of the theories and programs to
determine their effectiveness. The author and publisher make no warranty of any kind, expressed or implied,
with regard to these programs or the documentation contained in this book.
The author and publisher shall not be liable in the event of incidental or consequential damages in connection
with, or arising out of, the furnishing, performance, or use of the programs, associated instructions, and/or
claims of productivity gains.
Trademarks
Trademarked names appear throughout this book. Rather than list the names and entities that own the
trademarks or insert a trademark symbol with each mention of the trademarked name, the publisher states that
it is using the names for editorial purposes only and to the benefit of the trademark owner, with no intention of
infringing upon that trademark.
The Coriolis Group, LLC
14455 N. Hayden Road
Suite 220
Scottsdale, Arizona 85260
(480) 483−0192
FAX (480) 483−0193
http://www.coriolis.com/
Library of Congress Cataloging−in−Publication Data
Odom, Sean
Cisco switching black book / by Sean Odom.
p. cm.
Includes index.
ISBN 1−57610−706−X
1. Packet switching (Data transmission) I. Title.
TK5105.3 .O36 2000
004.6’6—dc21 00−064415
10 9 8 7 6 5 4 3 2 1
President and CEO
Keith Weiskamp
Publisher
1
Steve Sayre
Acquisitions Editor
Charlotte Carpentier
Product Marketing Manager
Tracy Rooney
Project Editor
Toni Zuccarini Ackley
Technical Reviewer
Deniss Suhanovs
Production Coordinator
Carla J. Schuder
Cover Designer
Jody Winkler
Layout Designer
April Nielsen
Dear Reader:
Coriolis Technology Press was founded to create a very elite group of books: the ones you keep closest to
your machine. Sure, everyone would like to have the Library of Congress at arm’s reach, but in the real world,
you have to choose the books you rely on every day very carefully.
To win a place for our books on that coveted shelf beside your PC, we guarantee several important qualities in
every book we publish. These qualities are:
•Technical accuracy—It’s no good if it doesn’t work. Every Coriolis Technology Press book is reviewed by
technical experts in the topic field, and is sent through several editing and proofreading passes in order to
create the piece of work you now hold in your hands.
•Innovative editorial design—We’ve put years of research and refinement into the ways we present
information in our books. Our books’ editorial approach is uniquely designed to reflect the way people learn
new technologies and search for solutions to technology problems.
•Practical focus—We put only pertinent information into our books and avoid any fluff. Every fact included
between these two covers must serve the mission of the book as a whole.
•Accessibility—The information in a book is worthless unless you can find it quickly when you need it. We
put a lot of effort into our indexes, and heavily cross−reference our chapters, to make it easy for you to move
right to the information you need.
Here at The Coriolis Group we have been publishing and packaging books, technical journals, and training
materials since 1989. We’re programmers and authors ourselves, and we take an ongoing active role in
defining what we publish and how we publish it. We have put a lot of thought into our books; please write to
us at ctp@coriolis.com and let us know what you think. We hope that you’re happy with the book in your
hands, and that in the future, when you reach for software development and networking information, you’ll
turn to one of our books first.
Keith Weiskamp President and CEO
2
Jeff Duntemann VP and Editorial Director
This book is dedicated to all those who endeavor to turn dreams into realities.
—Sean Odom
To my wife, Sonia, and my daughter, Sabrina.
—Hanson Nottingham
About the Authors
Sean Odom is a CCNP, MCSE, and CNX−Ethernet. He has been in the computer networking field for over
12 years and can be found instructing a number of Cisco courses, including the Switching and Remote Access
courses for Globalnet Training Solutions, Inc. (http://www.globalnettraining.com/). Sean is a former
president and currently on the board of the Sacramento Placer County Cisco Users Group (SPCCUG). In
addition, Sean has been a consultant for many companies including Advanced Computer Systems, American
Licorice, CH2M Hill, The Money Store, NCR, Wells Fargo Bank, and Intel. Sean has authored and
co−authored many industry books, labs, and white papers. You can reach Sean by email at
(sodom@rcsis.com) or see his Web site at http://www.thequestforcertification.com/.
Hanson Nottingham is a CCNA, MCSE, and MCP+I. He is an experienced Windows NT Systems Engineer
with over eight years experience in the Information Systems industry. Hanson is currently working as a
systems manager on the E:Services NT Team at Hewlett−Packard Company. Prior to HP, Hanson helped
manage Vision Service Plan’s Web farm as an Internet systems engineer. He specializes in Web farm
management and integration, SOHO network designs, and e−commerce solutions. Hanson is currently
working to further his Cisco Certified Networking Professional certification.
Acknowledgments
It’s always exciting when you get to the acknowledgments because that means the book is almost done. First
off, I must thank Erin for putting up with me during the writing of this book. She is a wonderful person who is
as smart as she is good looking and puts up with a lot of extra responsibility while I am working on books. I
also need to thank Albert Ip and Hanson Nottingham for their defined knowledge of the Cisco switches.
Thanks to my favorite English teacher, Mr. Strange, for being the one who originally thought I would be a
great writer some day, and I guess it shows here in my third book. Coriolis deserves many thanks. A few
people in particular at Coriolis need to be thanked: Steve Sayre, for believing in my idea of a Cisco SwitchingBlack Book; my project editor for the second time, Toni Zuccarini Ackley; Tiffany Taylor for finding all my
mistakes; Charlotte Carpentier and Shari Jo Hehr for handling the many contract issues for this book; Jody
Winkler for making the cover; Carla Schuder for making the inside of the book look good; and Paul LoPresto
for all his help in acquisitions.
—Sean Odom
Sean, thank you for giving me the opportunity and the privilege to become a co−author on this book—I
appreciate all your help, assistance, and encouragement! To my wonderful wife, Sonia, and my beautiful
daughter, Sabrina, thank you for giving me the time—dealing with my complicated and difficult schedules I
know has not been easy and your support does not go unnoticed! To Toni and the rest of the Coriolis team,
thank you for this opportunity and your undying patience throughout my process development learning
curve—I owe you guys mochas!
—Hanson Nottingham
3
Introduction
Overview
For many years I have been a consultant for different companies and have written books on switch and router
configurations and troubleshooting. During my years as a consultant I have had to either install, administer, or
troubleshoot switching problems and configurations for switches without a good handbook. I have constantly
gone through bookstores looking for a book on Cisco switch troubleshooting and configurations that didn’t
deal with a Cisco curriculum. Guess what? I couldn’t find one!
I have written books related to the CCDP and CCNP curricula and always thought about writing a book that
concentrated on Cisco switches. One day I was walking through a bookstore and noticed a book from The
Coriolis Group called Cisco Routers for IP Routing Little Black Book. I immediately thought to myself that a
Cisco Switching Little Black Book would be a great configuration handbook for many people. After contacting
Coriolis and pitching them the idea for the book, I received a call from Steve Sayre, the publisher at Coriolis,
who was excited about publishing a book of this nature. As I pondered and started putting my idea into an
outline, I realized that I could not place everything that an administrator needed in a Little Black Book.
To make a long story short, a few months later, with a great big outline and help from Albert Ip and Hanson
Nottingham, the book became this Black Book—the most feature−packed handbook for Cisco switching an
administrator can buy. Not only do we cover the Cisco Catalyst switching line but we also cover the
LightStream ATM switch series, Gigabit Switch Router Series (GSR), and the IGX and MGX WAN switch
series.
Thanks for buying the Cisco Switching Black Book.
Is This Book for You?
The Cisco Switching Black Book was written with the intermediate or advanced user in mind. Among the
topics that are covered, are:
The examples in the Immediate Solutions are intended to teach you the basic steps in configuring Cisco
Catalyst switches and their interfaces. Primarily, the Immediate Solutions will cover the information discussed
in the In Depth section of each chapter. When we explain each scenario we will use the following notations:
<Italics in angle brackets> will be used to denote command elements that have a specific value that
•
needs to be input, such as characters or numbers. Occasionally some other entry will be needed,
which will be explained in each individual instance.
[Text in square brackets] is used to denote optional commands that can be configured.•
4
Words in brackets that are separated by bars are used when indicating that there are multiple choices
•
of commands. For example, when configuring VTP you can enable the trunk port to choose one
mode: on, off, desirable, or auto mode. This will be shown like this: [on|off|desirable|auto].
Knowledge of what configuration mode you are in and how to enter each configuration mode on the Cisco
Command Line Interface is important. Knowing what each mode configures will aid you in using the proper
configuration mode. The Set/Clear command−based IOS CLI uses similar command modes as the Cisco CLI
used on Cisco routers and switches, but uses mainly the enable, set, show, and clear commands. Chapter 1
will cover the different CLI command modes.
The Black Book Philosophy
Written by experienced professionals, Coriolis Black Books provide immediate solutions to global
programming and administrative challenges, helping you complete specific tasks, especially critical ones that
are not well documented in other books. The Black Book’s unique two−part chapter format—thorough
technical overviews followed by practical immediate solutions—is structured to help you use your knowledge,
solve problems, and quickly master complex technical issues to become an expert. By breaking down
complex topics into easily manageable components, this format helps you quickly find what you’re looking
for, with commands, jump tables, and step−by−step configurations located in the Immediate Solutions section.
I welcome your feedback on this book. You can either email The Coriolis Group at ctp@coriolis.com or
email me directly at sodom@rcsis.com. Errata, updates, information on classes I teach, and more are
available at my Web site: http://www.thequestforcertification.com/.
5
Chapter 1: Network Switching Fundamentals
In Depth
Although writing the first paragraph of a book is probably the least important part, it’s invariably the most
difficult section to write. To get a good picture of the different parts of networking, readers need to know
where networking began and the history behind the networks of today. You may have seen a lot of what is in
the first section of this chapter in any basic networking course, such as Networking Essentials; or you may
have covered most of it in a CCNA class; but a refresher never hurt.
In this chapter, you will become acquainted with the history of networks and how networks evolved into those
you see in today’s corporate environments. I will also discuss the inventors of the different types of
networking equipment found at each layer of the network.
As we progress through the chapter I will also cover the different network architectures, from legacy networks
to the fast high−speed media types found in today’s networks. A clear understanding of the networking
technologies and challenges found at each layer of the network will aid you in assessing problems with the
switches you’ll deal with later.
I have a favorite quote that helps me to remember why I continuously study, so that I can better support my
customers’ equipment. It is a quote by Albert Einstein, and I remember it from one of my mentors: “The
significant [technical] problems we face cannot be solved by the same level of thinking that created them.”
This chapter will contain some of the following information:
The history of networking•
The different pieces of networking equipment•
How to identify problems in a flat network topology•
The how to’s and the when to’s of upgrading to a switched network•
When to upgrade your flat topology network•
Network upgrade planning and basic strategies•
Two terms to keep in mind when reading this chapter are resource nodes and demand nodes. A resource node
is a node on an interface attached to a device that provides resources to the network. These nodes can be
everything from printers, servers, and mainframes, to wide area network (WAN) routers. A demand node is an
interface on the network that makes requests or queries to the resource nodes. The interfaces can be devices
such as workstations, terminals, or even client applications. Network conversations occur when resource
nodes and demand nodes send a series of requests and responses through the network.
Physical Media and Switching Types
The following are the most popular types of physical media in use today:
Ethernet—Based on the Institute of Electrical and Electronics Engineers (IEEE) 802.3 standard.
•
However, it doesn’t rely on the Carrier Sense Multiple Access Collision Detection (CSMA/CD)
technology. It includes 10Mbps LANs, as well as Fast Ethernet and Gigabit Ethernet.
Token−Ring—Not as popular as Ethernet switching. Token−Ring switching can also be used to
•
improve LAN performance.
FDDI—Rarely used, chiefly due to the high expense of Fiber Distributed Data Interface (FDDI)
•
equipment and cabling.
The following are some of the protocol and physical interface switching types in use today:
6
Port switching—Takes place in the backplane of a shared hub. For instance, ports 1, 2, and 3 could be
•
connected to backplane 1, whereas ports 4, 5, and 6 could be connected to backplane 2. This method
is typically used to form a collapsed backbone and to provide some improvements in the network.
Cell switching—Uses Asynchronous Transfer Mode (ATM) as the underlying technology. Switch
•
paths can be either permanent virtual circuits (PVCs) that never go away, or switched virtual circuits
(SVCs) that are built up, used, and torn down when you’re finished.
A Bit of History
The first local area networks (LANs) began as a result of the introduction of personal computers into the
workplace environment. As computers became more common, the need arose to share resources, such as
printers or files. These early networks were pretty simple, with a handful of computers sharing a few printers
and not much more. As more items such as servers, applications, and peripherals came along, the increasing
numbers of interfaces—along with application designs that could take advantage of the network—created a
weakness in the current network design.
The limitations of traditional Ethernet technology brought forth a number of innovations that soon became
standard in the Ethernet protocol. Innovations such as full duplexing, Fast Ethernet, and Gigabit Ethernet
began to appear—innovations that have also made possible a transition to switches from shared hubs.
Other limitations to the way networks operated in a shared environment created a need for alternative methods
to permit the use of bandwidth−intensive applications such as video and voice. Switches are one of these
alternative methods. In many respects, switches are relatively simple devices. A switch’s design and
self−learning features require very little manual configuration to get it up and running. To properly use these
devices in your network, you must have an in−depth knowledge of the issues involved in implementing
switching.
Knowing the basics of Ethernet technology can help you effectively troubleshoot and install switches in the
network. You also need a good grasp of the different technologies and how switches work, as well as the
constraints of each type of device you may use in the network. As you read the following sections, make sure
you get a clear understanding of the fundamentals and basics of Ethernet technology.
The types of devices you use in the network have important implications for network performance. For
example, bridges and routers are both devices that network administrators use to extend the capabilities of
their networks. Both of them have advantages and disadvantages.
Bridges, for example, can easily solve distance limitations and increase the number of stations you can have
on a network, but they can have real problems with broadcast traffic. Routers can be used to prevent this
problem, but they increase the time it takes to forward the traffic.
This has been the pattern throughout the history of networking. When a new product is introduced, problems
or bottlenecks are soon found that limit the product’s usefulness. Then, innovations are invented or
implemented to aid the product and allow it to perform better. To see this occurrence in action, let’s take a
look at some of the traditional network architectures. As you will see in upcoming sections, the pattern of new
innovation after new innovation started in the earliest days of networking and continues in today’s networks.
Networking Architectures
Network designers from the beginnings of networking were faced with the limitations of the LAN topologies.
In modern corporate networks, LAN topologies such as Ethernet, Token Ring, and FDDI are used to provide
network connectivity. Network designers often try to deploy a design that uses the fastest functionality that
can be applied to the physical cabling.
7
Many different types of physical cable media have been introduced over the years, such as Token Ring, FDDI,
and Ethernet. At one time, Token Ring was seen as a technically superior product and a viable alternative to
Ethernet. Many networks still contain Token Ring, but very few new Token Ring installations are being
implemented. One reason is that Token Ring is an IBM product with very little support from other vendors.
Also, the prices of Token Ring networks are substantially higher than those of Ethernet networks.
FDDI networks share some of the limitations of Token Ring. Like Token Ring, FDDI offers excellent benefits
in the area of high−speed performance and redundancy. Unfortunately, however, it has the same high
equipment and installation costs. More vendors are beginning to recognize FDDI and are offering support,
services, and installation for it—especially for network backbones.
Network backbones are generally high−speed links running between segments of the network. Normally,
backbone cable links run between two routers; but they can also be found between two switches or a switch
and a router.
Ethernet has by far overwhelmed the market and obtained the highest market share. Ethernet networks are
open−standards based, more cost−effective than other types of physical media, and have a large base of
vendors that supply the different Ethernet products. The biggest benefit that makes Ethernet so popular is the
large number of technical professionals who understand how to implement and support it.
Early networks were modeled on the peer−to−peer networking model. These worked well for the small
number of nodes, but as networks grew they evolved into the client/server network model of today. Let’s take
a look at these two models in more depth.
Peer−to−Peer Networking Model
A small, flat network or LAN often contains multiple segments connected with hubs, bridges, and repeaters.
This is an Open Systems Interconnection (OSI) Reference Model Layer 2 network that can actually be
connected to a router for access to a WAN connection. In this topology, every network node sees the
conversations of every other network node.
In terms of scalability, the peer−to−peer networking model has some major limitations—especially with the
technologies that companies must utilize to stay ahead in their particular fields. No quality of service,
prioritizing of data, redundant links, or data security can be implemented here, other than encryption. Every
node sees every packet on the network. The hub merely forwards the data it receives out of every port, as
shown in Figure 1.1.
Figure 1.1: A flat network topology.
Early networks consisted of a single LAN with a number of workstations running peer−to−peer networks and
sharing files, printers, and other resources. Peer−to−peer networks share data with one another in a
non−centralized fashion and can span only a very limited area, such as a room or building.
8
Client/Server Network Model
Peer−to−peer model networks evolved into the client/server model, in which the server shares applications
and data storage with the clients in a somewhat more centralized network. This setup includes a little more
security, provided by the operating system, and ease of administration for the multiple users trying to access
data.
A LAN in this environment consists of a physical wire connecting the devices. In this model, LANs enable
multiple users in a relatively small geographical area to exchange files and messages, as well as to access
shared resources such as file servers and printers. The isolation of these LANs makes communication between
different offices or departments difficult, if not impossible. Duplication of resources means that the same
hardware and software have to be supplied to each office or department, along with separate support staff for
each individual LAN.
WANs soon developed to overcome the limitations of LANs. WANs can connect LANs across normal
telephone lines or other digital media (including satellites), thereby ignoring geographical limitations in
dispersing resources to network clients.
In a traditional LAN, many limitations directly impact network users. Almost anyone who has ever used a
shared network has had to contend with the other users of that network and experienced the impacts. These
effects include such things as slow network response times, making for poor network performance. They are
due to the nature of shared environments.
When collision rates increase, the usefulness of the bandwidth decreases. As applications begin having to
resend data due to excessive collisions, the amount of bandwidth used increases and the response time for
users increases. As the number of users increases, the number of requests for network resources rises, as well.
This increase boosts the amount of traffic on the physical network media and raises the number of data
collisions in the network. This is when you begin to receive more complaints from the network’s users
regarding response times and timeouts. These are all telltale signs that you need a switched Ethernet network.
Later in this chapter, we will talk more about monitoring networks and solutions to these problems. But before
we cover how to monitor, design, and upgrade your network, let’s look at the devices you will find in the
network.
The Pieces of Technology
In 1980, a group of vendors consisting of Digital Equipment Corporation (DEC), Intel, and Xerox created
what was known as the DIX standard. Ultimately, after a few modifications, it became the IEEE 802.3
standard. It is the 802.3 standard that most people associate with the term Ethernet.
The Ethernet networking technology was invented by Robert M. Metcalfe while he was working at the Xerox
Palo Alto Research Center in the early 1970s. It was originally designed to help support research on the
“office of the future.” At first, the network’s speed was limited to 3Mbps.
Ethernet is a multiaccess, packet−switched system with very democratic principles. The stations themselves
provide access to the network, and all devices on an Ethernet LAN can access the LAN at any time. Ethernet
signals are transmitted serially, one bit at a time, over a shared channel available to every attached station.
To reduce the likelihood of multiple stations transmitting at the same time, Ethernet LANs use a mechanism
known as Carrier Sense Multiple Access Collision Detection (CSMA/CD) to listen to the network and see if it
is in use. If a station has data to transmit, and the network is not in use, the station sends the data. If two
stations transmit at the same time, a collision occurs. The stations are notified of this event, and they instantly
reschedule their transmissions using a specially designed back−off algorithm. As part of this algorithm, each
station involved chooses a random time interval to schedule the retransmission of the frame. In effect, this
process keeps the stations from making transmission attempts at the same time and prevents a collision.
9
After each frame transmission, all stations on the network contend equally for the next frame transmission.
This competition allows access to the network channel in a fair manner. It also ensures that no single station
can lock out the other stations from accessing the network. Access to the shared channel is determined by the
Media Access Control (MAC) mechanism on each Network Interface Card (NIC) located in each network
node. The MAC address uses a physical address which, in terms of the OSI Reference Model, contains the
lowest level address. This is the address used by a switch. The router at Layer 3 uses a protocol address,
which is referred as a logical address.
CSMA/CD is the tool that allows collisions to be detected. Each collision of frames on the network reduces
the amount of network bandwidth that can be used to send information across the physical wire. CSMA/CD
also forces every device on the network to analyze each individual frame and determine if the device was the
intended recipient of the packet. The process of decoding and analyzing each individual packet generates
additional CPU usage on each machine, which degrades each machine’s performance.
As networks grew in popularity, they also began to grow in size and complexity. For the most part, networks
began as small isolated islands of computers. In many of the early environments, the network was installed
over a weekend—when you came in on Monday, a fat orange cable was threaded throughout the organization,
connecting all the devices. A method of connecting these segments had to be derived. In the next few sections,
we will look at a number of approaches by which networks can be connected. We will look at repeaters, hubs,
bridges, and routers, and demonstrate the benefits and drawbacks to each approach.
Repeaters
The first LANs were designed using thick coaxial cables, with each station physically tapping into the cable.
In order to extend the distance and overcome other limitations on this type of installation, a device known as a
repeater is used. Essentially, a repeater consists of a pair of back−to−back transceivers. The transmit wire on
one transceiver is hooked to the receive wire on the other, so that bits received by one transceiver are
immediately retransmitted by the other.
Repeaters work by regenerating the signals from one segment to another, and they allow networks to
overcome distance limitations and other factors. Repeaters amplify the signal to further transmit it on the
segment because there is a loss in signal energy caused by the length of the cabling. When data travels
through the physical cable it loses strength the further it travels. This loss of the signal strength is referred to
as attenuation.
These devices do not create separate networks; instead, they simply extend an existing one. A standard rule of
thumb is that no more than three repeaters may be located between any two stations. This is often referred to
as the 5−4−3 rule, which states that no more than 5 segments may be attached by no more than 4 repeaters,
with no more than 3 segments populated with workstations. This limitation prevents propagation delay, which
is the time it takes for the packet to go from the beginning of the link to the opposite end.
As you can imagine, in the early LANs this method resulted in a host of performance and fault−isolation
problems. As LANs multiplied, a more structured approach called 10BaseT was introduced. This method
consists of attaching all the devices to a hub in the wiring closet. All stations are connected in a
point−to−point configuration between the interface and the hub.
Hubs
A hub, also known as a concentrator, is a device containing a grouping of repeaters. Similar to repeaters, hubs
are found at the Physical layer of the OSI Model. These devices simply collect and retransmit bits. Hubs are
used to connect multiple cable runs in a star−wired network topology into a single network. This design is
similar to the spokes of a wheel converging on the center of the wheel.
Many benefits derive from this type of setup, such as allowing interdepartmental connections between hubs,
extending the maximum distance between any pair of nodes on the network, and improving the ability to
isolate problems from the rest of the network.
10
Six types of hubs are found in the network:
Active hubs—Act as repeaters and eliminate attenuation by amplifying the signals they replicate to all
•
the attached ports.
Backbone hubs—Collect other hubs into a single collection point. This type of design is also known
•
as a multitiered design. In a typical setup, servers and other critical devices are on high−speed Fast
Ethernet or Gigabit uplinks. This setup creates a very fast connection to the servers that the
lower−speed networks can use to prevent the server or the path to the server from being a bottleneck
in the network.
Intelligent hubs—Contain logic circuits that shut down a port if the traffic indicates that malformed
•
frames are the rule rather than the exception.
Managed hubs—Have Application layer software installed so that they can be remotely managed.
•
Network management software is very popular in organizations that have staff responsible for a
network spread over multiple buildings.
Passive hubs—Aid in producing attenuation. They do not amplify the signals they replicate to all the
•
attached ports. These are the opposite of active hubs.
Stackable hubs—Have a cable to connect hubs that are in the same location without requiring the data
•
to pass through multiple hubs. This setup is commonly referred to as daisy chaining.
In all of these types of hub configurations, one crucial problem exists: All stations share the bandwidth, and
they all remain in the same collision domain. As a result, whenever two or more stations transmit
simultaneously on any hub, there is a strong likelihood that a collision will occur. These collisions lead to
congestion during high−traffic loads. As the number of stations increases, each station gets a smaller portion
of the LAN bandwidth. Hubs do not provide microsegmentation and leave only one collision domain.
Bridges
A bridge is a relatively simple device consisting of a pair of interfaces with some packet buffering and simple
logic. The bridge receives a packet on one interface, stores it in a buffer, and immediately queues it for
transmission by the other interface. The two cables each experience collisions, but collisions on one cable do
not cause collisions on the other. The cables are in separate collision domains.
Note Some bridges are capable of connecting dissimilar topologies.
The term bridging refers to a technology in which a device known as a bridge connects two or more LAN
segments. Bridges are OSI Data Link layer, or Layer 2, devices that were originally designed to connect two
network segments. Multiport bridges were introduced later to connect more than two network segments, and
they are still in use in many networks today. These devices analyze the frames as they come in and make
forwarding decisions based on information in the frames themselves.
To do its job effectively, a bridge provides three separate functions:
Filtering the frames that the bridge receives to determine if the frame should be forwarded•
Forwarding the frames that need to be forwarded to the proper interface•
Eliminating attenuation by amplifying received data signals•
Bridges learn the location of the network stations without any intervention from a network administrator or
any manual configuration of the bridge software. This process is commonly referred to as self−learning.
When a bridge is turned on and begins to operate, it examines the MAC addresses located in the headers of
frames passed through the network. As the traffic passes through the bridge, the bridge builds a table of
known source addresses, assuming the port from which the bridge received the frame is the port to which the
device is a sending device is attached.
In this table, an entry exists that contains the MAC address of each node along with the bridge interface and
port on which it resides. If the bridge knows that the destination is on the same segment as the source, it drops
the packet because there is no need to transmit it. If the bridge knows that the destination is on another
11
segment, it transmits the packet on that segment or port to that segment only. If the bridge does not know the
destination segment, the bridge transmits a copy of the frame to all the interface ports in the source segment
using a technique known as flooding. For each packet an interface receives, the bridge stores in its table the
following information:
The frame’s source address•
The interface the frame arrived on•
The time at which the switch port received the source address and entered it into the switching table•
Note Bridges and switches are logically equivalent.
There are four kinds of bridges:
Transparent bridge—Primarily used in Ethernet environments. They are called transparent bridges
•
because their presence and operation are transparent to network hosts. Transparent bridges learn and
forward packets in the manner described earlier.
Source−route bridge—Primarily used in Token Ring environments. They are called source−route
•
bridges because they assume that the complete source−to−destination route is placed in frames sent
by the source.
Translational bridge—Translators between different media types, such as Token Ring and Ethernet.•
Source−route transparent bridge—A combination of transparent bridging and source−route bridging
•
that enables communication in mixed Ethernet and Token Ring environments.
Broadcasts are the biggest problem with bridges. Some bridges help reduce network traffic by filtering
packets and allowing them to be forwarded only if needed. Bridges also forward broadcasts to devices on all
segments of the network. As networks grow, so does broadcast traffic. Instead of frames being broadcast
through a limited number of devices, bridges often allow hundreds of devices on multiple segments to
broadcast data to all the devices. As a result, all devices on all segments of the network are now processing
data intended for one device. Excessive broadcasts reduce the amount of bandwidth available to end users.
This situation causes bandwidth problems called network broadcast storms. Broadcast storms occur when
broadcasts throughout the LAN use up all available bandwidth, thus grinding the network to a halt.
Network performance is most often affected by three types of broadcast traffic: inquiries about the availability
of a device, advertisements for a component’s status on the network, and inquiries from one device trying to
locate another device. The following are the typical types of network broadcasts:
Address Resolution Protocol (ARP)•
Internetwork Packet Exchange (IPX) Get Nearest Server (GNS) requests•
IPX Service Advertising Protocol (SAP)•
Multicast traffic broadcasts•
NetBIOS name requests•
These broadcasts are built into the network protocols and are essential to the operation of the network devices
using these protocols.
Due to the overhead involved in forwarding packets, bridges also introduce a delay in forwarding traffic. This
delay is known as latency. Latency delay is measured from the moment a packet enters the input port on the
switch until the time the bridge forwards the packet out the exit port. Bridges can introduce 20 to 30 percent
loss of throughput for some applications. Latency is a big problem with some timing−dependent technologies,
such as mainframe connectivity, video, or voice.
High levels of latency can result in loss of connections and noticeable video and voice degradation. The
inherent problems of bridging over multiple segments including those of different LAN types with Layer 2
devices became a problem to network administrators. To overcome these issues, a device called a router,
operating at OSI Layer 3, was introduced.
12
Routers
Routers are devices that operate at Layer 3 of the OSI Model. Routers can be used to connect more than one
Ethernet segment with or without bridging. Routers perform the same basic functions as bridges and also
forward information and filter broadcasts between multiple segments. Figure 1.2 shows routers segmenting
multiple network segments. Using an OSI network Layer 3 solution, routers logically segment traffic into
subnets.
Figure 1.2: Routers connecting multiple segments.
Routers were originally introduced to connect dissimilar network media types as well as to provide a means to
route traffic, filter broadcasts across multiple segments, and improve overall performance. This approach
eliminated broadcasts over multiple segments by filtering broadcasts. However, routers became a bottleneck
in some networks and also resulted in a loss of throughput for some types of traffic.
When you are connecting large networks, or when you are connecting networks to a WAN, routers are very
important. Routers will perform media conversion, adjusting the data link protocol as necessary. With a
router, as well as with some bridges, you can connect an Ethernet network and a Token Ring network.
Routers do have some disadvantages. The cost of routers is very high, so they are an expensive way to
segment networks. If protocol routing is necessary, you must pay this cost. Routers are also difficult to
configure and maintain, meaning that you will have a difficult time keeping the network up and running.
Knowledgeable workers who understand routing can be expensive.
Routers are also somewhat limited in their performance, especially in the areas of latency and forwarding
rates. Routers add about 40 percent additional latency from the time packets arrive at the router to the time
they exit the router. Higher latency is primarily due to the fact that routing requires more packet assembly and
disassembly. These disadvantages force network administrators to look elsewhere when designing many large
network installations.
Switches
A new option had to be developed to overcome the problems associated with bridges and routers. These new
devices were called switches. The term switching was originally applied to packet−switch technologies, such
as Link Access Procedure, Balanced (LAPB); Frame Relay; Switched Multimegabit Data Service (SMDS);
and X.25. Today, switching is more commonly associated with LAN switching and refers to a technology that
is similar to a bridge in many ways.
Switches allow fast data transfers without introducing the latency typically associated with bridging. They
create a one−to−one dedicated network segment for each device on the network and interconnect these
segments by using an extremely fast, high−capacity infrastructure that provides optimal transport of data on a
LAN; this structure is commonly referred to as a backplane. This setup reduces competition for bandwidth on
the network, allows maximum utilization of the network, and increases flexibility for network designers and
implementers.
Ethernet switches provide a number of enhancements over shared networks. Among the most important is
microsegmentation, which is the ability to divide networks into smaller and faster segments that can operate at
the maximum possible speed of the wire (also known as wire−speed).
13
To improving network performance, switches must address three issues:
They must stop unneeded traffic from crossing network segments.•
They must allow multiple communication paths between segments.•
They cannot introduce performance degradation.•
Routers are also used to improve performance. Routers are typically attached to switches to connect multiple
LAN segments. A switch forwards the traffic to the port on the switch to which the destination device is
connected, which in turn reduces the traffic to the other devices on the network. Information from the sending
device is routed directly to the receiving device. No device other than the router, switch, and end nodes sees or
processes the information.
The network now becomes less saturated, more secure, and more efficient at processing information, and
precious processor time is freed on the local devices. Routers today are typically placed at the edge of the
network and are used to connect WANs, filter traffic, and provide security. See Figure 1.3.
Figure 1.3: Routers and switches
Like bridges, switches perform at OSI Layer 2 by examining the packets and building a forwarding table
based on what they hear. Switches differ from bridges by helping to meet the following needs for network
designers and administrators:
Provide deterministic paths•
Relieve network bottlenecks•
Provide deterministic failover for redundancy•
Allow scalable network growth•
Provide fast convergence•
Act as a means to centralize applications and servers•
Have the capacity to reduce latency•
Network Design
When designing or upgrading your network, you need to keep some basic rules of segmenting in mind. You
segment your network primarily to relieve network congestion and route data as quickly and efficiently as
possible. Segmentation is often necessary to satisfy the bandwidth requirements of a new application or type
of information that the network needs to support. Other times, it may be needed due to the increased traffic on
the segment or subnet. You should also plan for increased levels of network usage or unplanned increases in
network population.
Some areas you need to consider are the types of nodes, user groups, security needs, population of the
network, applications used, and the network needs for all the interfaces on the network. When designing your
network, you should create it in a hierarchical manner. Doing so provides you with the ability to easily make
additions to your network. Another important consideration should be how your data flows through the
network.
For example, let’s say your users are intermingled with your servers in the same geographical location. If you
create a switched network in which the users’ data must be switched through a number of links to another
geographical area and then back again to create a connection between the users and file servers, you have not
14
Loading...
+ 381 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.