- Shopping Bag ( 0 items )
Ships from: Bensalem, PA
Usually ships in 1-2 business days
Ships from: Southampton, PA
Usually ships in 1-2 business days
Ships from: Philadelphia, PA
Usually ships in 1-2 business days
Ships from: Murphy, TX
Usually ships in 1-2 business days
Ships from: Chatham, NJ
Usually ships in 1-2 business days
Ships from: acton, MA
Usually ships in 1-2 business days
• In-depth coverage of every CCDA exam objective
• Practical information on Cisco design solutions
• Hundreds of challenging practice questions, in the book and on the CD
• Leading-edge exam preparation software, including a test engine, electronic flashcards, and simulation software
Authoritative coverage of all exam objectives, including:
• Gathering and evaluating information regarding current and future network requirements
• Identifying possible opportunities for network performance improvement
• Evaluating solutions for meeting IP addressing, routing protocol, and network management needs
• Incorporating equipment and technology within a campus design
• Applying the Enterprise Composite Network Model
• Addressing the issues of delivering voice traffic over a data network
• Evaluating solutions for compliance with SAFE architecture
• Developing implementation, prototype testing, and verification plans
Note: CD-ROM/DVD and other supplementary materials are not included as part of eBook file.
CCDA EXAM TOPICS COVERED IN THIS CHAPTER:
As your mom probably told you, there's really no better place to start than at the beginning. But what she likely didn't warn you is that any process-internetworking being a classic example-takes its share of rabbit trails that dead-end. Other paths flourish into full-scale systems. One thing is certain: the changes in this industry have been mercurial. One day someone has a germ of a thought, and a few days later a new field emerges from that embryonic idea. Following these trails, however, can be a bit of a challenge.
So this is your primer-a course in the ABCs of internetworks. This opening chapter will examine the history of internetworking and then establish how it evolved into the technology of today. We'll also describe the LAN and WAN equipment that's typically found in a modern internetworking environment. A necessary prerequisite to this is to fully understand the OSI reference model. I'll show you how the layered approach to application development has created the present internetworking standards that shape how modern internetworking takes place. So relax; I'll take you step-by-step through the fundamentals you need to learn.
The main topics addressed in this chapter are
* Identify and describe the functions of each of the seven layers of the OSI reference model.
* Describe the basic process of communication between the layers of the OSI reference model.
* Describe connection-oriented network service and connectionless network service and identify the key differences between them.
* Describe the basic process of information exchange between two applications across a network.
* Define flow control and describe the three basic methods used in networking.
* Identify the major standards organizations and bodies that specify internetworking standards.
* Define multiplexing and describe its function in internetworking. Internetworking Fundamentals
To understand internetworking, let's begin by going back to the origins of networking and following its evolutionary path. We'll look at how internetworks have developed along this path and finish with a discussion that describes the demands of a typical, contemporary internetwork.
Evolution of Internetworking
As you might recall, network communications in the 1960s and 1970s were centered on the mainframe. Machines called dumb terminals would access the mainframe over low-speed lines. This arrangement was referred to as a centralized computing environment because all the processing took place in one central location. A classic example of a centralized computing environment is found in IBM's Systems Network Architecture (SNA) using multi-drop lines and X.25 packet switching.
Through the dumb terminal, the user could run programs, access resources, and copy files. The mainframe would serve to authenticate or verify the user, then coordinate the user and the program. This method worked quite well and was actually very straightforward-with one computer. But relatively early on, the idea of hooking computers together to talk to one another became an obvious no-brainer. However, things become a little more complex when using multiple computers. When several machines need to be coordinated, you have to be aware of things like
* Error detection and correction
* Time synchronization
* Transmission coordination
Then the 1980s dawned. The PC became widely available and changed networking forever. At this point, printers were attached to PCs with serial cables that were typically shared with A/B switch boxes. This meant only two people could use the same printer. Pretty soon, boxes became available that would allow five or ten users to be plugged into and share the same printer, but since printer queuing hadn't been developed yet, it still meant only one person could print at a given time. I have a sick-minded friend who fondly remembers the days when everyone gathered around the printer waiting for their stuff-a great way to get the skinny on office gossip but a huge time-waster. And if you were on deadline, forget it! The need to have many printers to adequately service all the users' jobs was an expensive reality indeed. So local area networks (LANs) were born to help reduce costs. Printer queuing-which requires creating a directory on a server in which print jobs are stored and from which they are later printed in the order received-made printing more efficient. But in order to make this process possible, the printers had to be connected to a LAN with that server. Only then could hundreds of users print to a printer (or printers) simultaneously.
Early LANs were small and isolated, and it wasn't long before the need to connect them became apparent. As necessity is the mother of invention, wide area networking soon evolved. Minicomputers and shared wide area networks (WANs) were created to address these growing business requirements.
Today, many businesses still have mainframe and LAN technologies working side by side. The migration of applications from central hosts to distributed servers has complicated computing needs considerably, resulting in new networking requirements and changing traffic patterns. The need for instant data transfer has motivated managers to jump at new technologies to stay ahead of demand and remain competitive. MIS (management information system) jobs have become full-time positions now, where network administration was once the responsibility of whoever happened to be sitting next to the server. Both the people and equipment working in an internetworking environment must be flexible, scalable, and adaptable to remain useful and succeed.
Internetworks are the communication structures that work to tie LANs and WANs together. Their primary function is to move information anywhere quickly, upon demand, and with complete integrity. Today's users have become increasingly dependent on their networks-watch the chaos that results around the office when a group of users' server or hub goes offline. Remember when fax machines came out? After a while, people stopped asking if you had a fax machine and just started asking for your fax number. Now, having Internet access from your PC is as common as having a fax once was. People used to ask me if I had e-mail, but now they just ask me for my e-mail address and web page URL!
What this means is that in order for today's corporations to remain competitive in the global market, the networks they depend on now have to efficiently manage, on a daily basis, some or all of the following:
* Graphics and imaging
* Files in the gigabyte range
* Client/server computing
* High network traffic loads
To be able to amply meet these needs, your company's Information Systems (IS) department must provide to users
* Increased bandwidth
* Bandwidth on demand
* Low delays
* High reliability
* Data, voice, and video capabilities on the same media
Also, the network of today must be readily adaptable to the applications of tomorrow. In the not-too-distant future, networks will need to be equipped to handle
* Voice over IP
* High-definition imaging
* Full-motion video
* Digitized audio
In short, for an internetwork to realize its purpose, it must be able to connect many different networks together to serve the organizations depending on it. And this connectivity must happen regardless of the type of physical media involved. Companies expanding their networks must overcome the limitations of physical and geographic boundaries. The Internet has served as a model to facilitate this growth.
LANs were designed to operate in limited geographic areas, such as one floor of a building or a single building. These networks were meant to be a cul-de-sac or small neighborhood of connections-everything close and within reach. LANs connect PCs together so that they can access network resources like printers and files. A LAN connects physically adjacent devices on the network media or cable. Typical LAN devices include repeaters, bridges, hubs, switches, routers, and gateways.
Repeaters regenerate and propagate signals from one network segment to another. They don't change the address or data; they only pass the data on. Repeaters can't filter packets, which are bits of data in a package. Even though a repeater helps to extend network reach by regenerating weak signals, be aware that using one will result in combining multiple network segments into a single network. In other words, it may connect pieces of your network that you don't want to talk to each other. Figure 1.1 shows what a repeater in a LAN looks like.
Sometimes repeaters are placed between the source and destination hosts to help compensate for signal deterioration due to attenuation. This results in latency-a delay in the time it takes the signal to travel between the source and destination hosts.
Bridges also regenerate signals, but they are more intelligent devices than repeaters. A bridge can read the destination MAC (Media Access Control) address or hardware address from the data frame and determine if the destination computer is on the local segment-the segment from which it received the frame-or on other network segments. If the destination computer is on the local segment, it won't forward the frame. If the destination computer isn't on the local segment, the bridge will forward the frame to all other network segments. Figure 1.2 shows how a bridge in a LAN works.
When segmenting an Ethernet LAN, using a bridge instead of a repeater can give you more bandwidth per user because it translates into fewer users per segment. But again, you can end up experiencing latency problems of up to 20-30 percent due to processing and filtering frames. Also, since bridges forward broadcasts to all other attached segments, broadcast storms can result from the broadcast packets propagating throughout the network. A broadcast storm is a network segment event; during one, a broadcast packet is sent in a perpetual loop until that segment becomes overloaded.
Hubs connect all computer LAN connections into one device or concentrator. Hubs can be considered multiport repeaters. PCs can be connected using coax or twisted-pair cable, or even radio frequency (RF). When one computer transmits a digital signal onto the network media, the signal is transmitted to all other segments that are plugged into the hub. Figure 1.3 shows a typical hub working in a LAN.
Unlike hubs, switches can run in full-duplex mode. This means that the computer and switch can both transmit and receive simultaneously. The biggest difference between a switch and a hub is that when a computer transmits a digital signal to a hub, it's then sent to all ports attached to that hub, whereas a switch will send it only to the specific port where the destination MAC address is located. Think of each switch port as being an extremely fast multi-port bridge.
Routers are a step up from bridges. Bridges filter by MAC address, but routers can filter by both hardware and network address (IP address). Repeaters operate at layer 1, bridges and switches layer 2, and routers layer 3 of the OSI reference model, which I will cover at length later in this chapter. When a bridge forwards a packet, it sends it out to all segments to which it is connected, whereas a router only forwards packets to the network segment that the packet is destined for. Routers economically prevent unnecessary network traffic from being sent over the network's segments by opening up the data packet and reading the network address before forwarding it. Figure 1.4 shows a typical LAN with a router segmenting the network.
Gateways are created with software that can be run on PCs and even routers. They link different programs or protocols and examine the entire packet, including the data portion, in order to translate incompatible protocols. For example, to exchange mail between a CCMail server and an Exchange server, you would have to install a mail gateway. Another example would be gateway services that run on a router. These can link an IP network to an IPX network so the users on the IP network can communicate transparently with the users on the IPX network and vice versa.
ATM (Asynchronous Transfer Mode) switches provide high-speed cell switching. ATM uses a cell relay technology that combines the advantages of both conventional circuit and packet-based systems.
WANs extend beyond the LAN to connect together networks located in different buildings, cities, states, and countries. WANs are typically, but not necessarily, limited to using the services of Regional Bell Operating Companies (RBOCs) like Pacific Bell, AT&T, Sprint, MCI, and others. Figure 1.5 shows a WAN connecting offices in three cities.
WANs are connected over links that operate at lower speeds than LANs. Typical WAN devices include
Routers In the WAN environment, routers offer both internetworking and WAN interface controls.
ATM switches ATM switches provide high-speed cell switching between both LANs and WANs.
X.25 and Frame Relay switches X.25 and Frame Relay switches connect private data over public data circuits using digital signals.
Modems Modems connect private data over public telephone circuits using analog signals.
CSUs/DSUs Components of customer premises equipment (CPE), channel service units (CSUs), and data service units (DSUs) are used to terminate a digital circuit at the customer site. These connect to a central office (CO), which is the telephone company switch located closest to the customer.
Communication servers Communication servers are typically dial-in/ dial-out servers that allow users to dial in from remote locations and attach to the LAN. Cisco's AS5300 series of communication servers are an example of devices that provide such services.
Multiplexors Multiplexors are devices that allow more than one signal to be sent out simultaneously over one physical circuit. The equipment is usually referred to as a mux.
The OSI Reference Model
When networks first came into being, computers could typically communicate only with computers from the same manufacturer. For example, companies ran either a complete DECnet solution or an IBM solution-not both together. Unfortunately, companies that worked together or with government agencies often had equipment from different sources. So, the ability to communicate through their networks was at a dead-end, or someone had to incur the exorbitant cost of switching their equipment to their partner's manufacturer. Ouch! In the early 1980s, the OSI (Open Systems Interconnection) reference model was created by the International Standards Organization (ISO) to break this barrier. This model was meant to help vendors create interoperable network devices. Since each vendor's products have distinctive attributes and incorporate trade "secrets," like world peace, it will probably never happen completely, but it's still a great goal.
The OSI model is the primary architectural model for networks. It describes how data and network information are communicated from applications on one computer, through the network media, to an application on another computer. The OSI reference model breaks this approach into layers.
Excerpted from CCDAsmall TM/small: Cisco Certified Design Associate Study Guide by Todd Lammle Excerpted by permission.
All rights reserved. No part of this excerpt may be reproduced or reprinted without permission in writing from the publisher.
Excerpts are provided by Dial-A-Book Inc. solely for the personal use of visitors to this web site.
|Ch. 1||Introduction to Internetworking||1|
|Ch. 2||LAN Segmentation||67|
|Ch. 3||Network Protocols||119|
|Ch. 4||Pre-Design Procedures||151|
|Ch. 5||Designing Modular Network Topologies||189|
|Ch. 6||Enterprise WAN Design||217|
|Ch. 7||Network Addressing and Naming||255|
|Ch. 8||Routing Protocols||311|
|Ch. 9||Link-State and Bridging Protocols||355|
|Ch. 10||Cisco IOS Software||405|
|Ch. 11||Network Management||431|
|Ch. 12||Post-Design Issues||457|
|Ch. 13||Designing Networks for Integrated Security and Voice Transport||477|
|App. A||Solutions to Case Studies||505|
Posted November 5, 2004
This book did not help prepare for the CCDA exam at all. Two of the biggest topics on the exam are VOIP and IPV6, which are two of the least discussed topics in the book.Was this review helpful? Yes NoThank you for your feedback. Report this reviewThank you, this review has been flagged.