4
Chapter 1
The Campus Network
Looking Backwards at Traditional Campus
Networks
I
n the 1990s, the traditional campus network started as one LAN and
grew and grew until segmentation needed to take place just to keep the net-
work up and running. In this era of rapid expansion, response time was sec-
ondary to just making sure the network was functioning.
And by looking at the technology, you can see why keeping the network
running was such a challenge. Typical campus networks ran on 10BaseT or
10Base2 (thinnet). As a result, the network was one large collision domain--
not to mention even one large broadcast domain. Despite these limitations,
Ethernet was used because it was scalable, effective, and somewhat inexpen-
sive compared to other options. ARCnet was used in some networks, but
Ethernet and ARCnet are not compatible, and the networks became two sep-
arate entities. ARCnet soon became history.
Because a campus network can easily span many buildings, bridges were
used to connect the buildings together; this broke up the collision domains,
but the network was still one large broadcast domain. More and more users
were attached to the hubs used in the network, and soon the performance of
the network was considered extremely slow.
Performance Problems and Solutions
Availability and performance are the major problems with traditional cam-
pus networks. Bandwidth helps compound these problems. The three per-
formance problems in traditional campus networks included collisions,
broadcasts and multicasts, and bandwidth.
Collisions
A campus network typically started as one large collision domain, so all
devices could see and also collide with each other. If a host had to broadcast,
then all other devices had to listen, even though they themselves were trying
to transmit. And if a device were to jabber (malfunction), it could almost
bring the entire network down.
Because routers didn't really become cost effective until the late 1980s,
bridges were used to break up collision domains, but the network was still
Copyright ©2000 SYBEX , Inc., Alameda, CA
www.sybex.com