Skip to main content

Module 2: WAN Technologies / Overview

Module 2: WAN Technologies/Overview
As the enterprise grows beyond a single location, it is necessary to interconnect the LANs in the various branches to form a wide-area network (WAN). This module examines some of the options available for these interconnections, the hardware needed to implement them, and the terminology used to discuss them.
There are many options currently available today for implementing WAN solutions. They differ in technology, speed, and cost. Familiarity with these technologies is an important part of network design and evaluation.
If all data traffic in an enterprise is within a single building, a LAN meets the needs of the organization. Buildings can be interconnected with high-speed data links to form a campus LAN if data must flow between buildings on a single campus. However, a WAN is needed to carry data if it must be transferred between geographically separate locations. Individual remote access to the LAN and connection of the LAN to the Internet are separate study topics, and will not be considered here.
Most students will not have the opportunity to design a new WAN, but many will be involved in designing additions and upgrades to existing WANs, and will be able to apply the techniques learned in this module.
Students completing this module should be able to:
  • Differentiate between a LAN and WAN
  • Identify the devices used in a WAN
  • List WAN standards
  • Describe WAN encapsulation
  • Classify the various WAN link options
  • Differentiate between packet-switched and circuit-switched WAN technologies
  • Compare and contrast current WAN technologies
  • Describe equipment involved in the implementation of various WAN services
  • Recommend a WAN service to an organization based on its needs
  • Describe DSL and cable modem connectivity basics
  • Describe a methodical procedure for designing WANs
  • Compare and contrast WAN topologies
  • Compare and contrast WAN design models
Recommend a WAN design to an organization based on its needs 

Comments

Popular posts from this blog

OSI layers / Peer-to-peer communications / TCP/IP model

OSI layers 2.3.4 This page discusses the seven layers of the OSI model. The OSI reference model is a framework that is used to understand how information travels throughout a network. The OSI reference model explains how packets travel through the various layers to another device on a network, even if the sender and destination have different types of network media. In the OSI reference model, there are seven numbered layers, each of which illustrates a particular network function. - Dividing the network into seven layers provides the following advantages: • It breaks network communication into smaller, more manageable parts. • It standardizes network components to allow multiple vendor development and support. • It allows different types of network hardware and software to communicate with each other. • It prevents changes in one layer from affecting other layers. • It divides network communication into smaller parts to make learning it easier to understand. In the foll...

Advantages and disadvantages of link-state routing

Advantages and disadvantages of link-state routing 2.1.5  This page lists the advantages and disadvantages of link-state routing protocols. The following are advantages of link-state routing protocols:  Link-state protocols use cost metrics to choose paths through the network. The cost metric reflects the capacity of the links on those paths. Link-state protocols use triggered updates and LSA floods to immediately report changes in the network topology to all routers in the network. This leads to fast convergence times. Each router has a complete and synchronized picture of the network. Therefore, it is very difficult for routing loops to occur. Routers use the latest information to make the best routing decisions. The link-state database sizes can be minimized with careful network design. This leads to smaller Dijkstra calculations and faster convergence. Every router, at the very least, maps the topology of it...

Ports for services

Ports for services 10.2.2  Services running on hosts must have a port number assigned to them so communication can occur. A remote host attempting to connect to a service expects that service to use specific transport layer protocols and ports. Some ports, which are defined in RFC 1700, are known as the well-known ports. These ports are reserved in both TCP and UDP.  These well-known ports define applications that run above the transport layer protocols. For example, a server that runs FTP will use ports 20 and 21 to forward TCP connections from clients to its FTP application. This allows the server to determine which service a client requests. TCP and UDP use port numbers to determine the correct service to which requests are forwarded. The next page will discuss ports in greater detail.